Multilayered Deception for Intrusion Detection and Prevention

ABSTRACT

Concepts and technologies are disclosed herein for multilayered deception for intrusion detection. According to various embodiments of the concepts and technologies disclosed herein, a multilayer deception system includes honey servers, honey files and folders, honey databases, and/or honey computers. A multilayer deception system controller generates honey activity between the honey entities and exposes a honey profile with contact information associated with a honey user. Contact directed at the honey user and/or activity at any of the honey entities can trigger alarms and/or indicate an attack, and can be analyzed to prevent future attacks.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/311,608, entitled “Multilayered Deception for Intrusion Detection andPrevention,” filed on Dec. 6, 2011, now allowed, which is incorporatedherein by reference in its entirety.

BACKGROUND

This application relates generally to network security. Morespecifically, the disclosure provided herein relates to multilayereddeception for intrusion detection and prevention.

Computer attacks are becoming increasingly sophisticated. Some attackerscreate attacks that operate over long periods of time and from multipleattack vectors. In some attacks, a computer intrusion is launched usinga single event such as a phishing message or spear-phishing message toinfect a computer of an employee or representative of a targetedorganization. Thus, for example, attackers may send a phishing email ormalware attachment to an employee of a company via email. When theemployee opens or executes the mail or message attachment, the computermay be compromised and key loggers, viruses, worms, and/or other threatsmay be initiated at the target computer.

Detecting malicious activities, such as data exfiltration, can be acomplex task that may require tracking network traffic data and/or loganalysis. As mentioned above, the attacks sometimes can be initiated bya user clicking on a link or executable script or macro within a singleemail or message. As such, these and other types of threats sometimesare not detected until data has already been exploited by the attack. Inother instances, the attacks are not detected until the attack hasalready ended.

SUMMARY

The present disclosure is directed to multilayered deception forintrusion detection and prevention. According to various embodiments ofthe concepts and technologies disclosed herein, a multilayer deceptionsystem controller operates on a private network such as a local network,a corporate intranet, or other network. The private network can beconfigured to communicate with, or allow access from, devices on apublic network such as the Internet. An attacker may identify a userassociated with the private network as a target for an attack. The usermay be identified by the attacker based, for example, upon a position ortitle at a company or due to other considerations. The multilayerdeception system controller is configured to identify possible orprobable targets of attacks and to protect the targets from exploitationusing multiple layers of deception.

In some embodiments, the multilayer deception system controller isconfigured to create a honey user and a honey profile for the honeyuser. A “honey user” can include, but is not limited to, arepresentation of a user. In some instances, the honey user is asoftware representation of the user and is based, completely or at leastin part, upon a real user identified as a probable or possible target ofan attack. The multilayer deception system controller can generate ahoney profile for the user based, at least partially, upon a realprofile for the real user. As such, the honey user can appear, from thehoney profile, to be the same person as the real user. The honey profilecan be exposed to public network. In some embodiments, for example, thehoney profile can be uploaded to a social networking site. Thus,attackers may target the honey user instead of, or in addition to, thereal user, thus redirecting possible attacks away from, and protecting,the user.

The multilayer deception system controller also can be configured togenerate various honey entities for emulating a computing environmentassociated with the real user and/or intercepting attacks targeted atthe real user. The honey entities can include, for example, honeycomputers, honey files and folders, honey servers, and/or honeydatabases. The multilayer deception system controller also can generatehoney activity between the honey entities to further deceive maliciousattackers and/or attacks. The honey entities and honey activity can behosted and/or executed by dedicated real or virtual resources, or hostedby resources associated with real entities such as a computer, server,database, files and folders, and the like. In some embodiments, thevarious honey entities are configured to operate independently asmultiple layers of traps for malicious attacks. In other embodiments,the various honey entities cooperate to provide a coordinatedmultilayered trap for attacks. For example, in some embodiments attackstargeted at the honey profile can be routed to the honey entitiesautomatically. In other embodiments, the honey entities operate on realresources such as users' computers, and are used to trap attacks beforethe attacks exploit real resources. In either or both embodiments, thehoney entities can be used to identify and/or isolate the attack fromother entities in the network including, for example, the real entitiesassociated with the real user. The multilayer deception systemcontroller can be configured to generate and track alarm conditionsand/or to modify access thresholds that can be used to identify activityas malicious or legitimate.

According to one aspect of the concepts and technologies disclosedherein, a method is disclosed. The method can include generating a honeyentity and an instance of honey activity associated with the honeyentity at a private network. The method also can include generating ahoney profile for the honey user, exposing the honey profile outside ofthe private network, detecting an interaction with the honey entity, andanalyzing the interaction to determine if the interaction corresponds toan attack.

According to various embodiments, the method also includes generatingthe honey profile associated with the honey user based, at leastpartially, upon a real profile of a real user associated with theprivate network. The real profile can include a first version of contactinformation and the honey profile can include a second version of thecontact information. In some instances, exposing the honey profileoutside the private network includes uploading information associatedwith the honey profile to a social networking service. Generating thehoney entity can include generating a honey server at the privatenetwork. Generating the honey entity can include generating a honeyfile, and the instance of honey activity can include activity betweenthe honey file and a computer operating on the private network.

In some embodiments, the computer can include a honey computer that canbe isolated from the real user. In some instances, the attack includes aspear-phishing email intended for delivery to a further computerassociated with the real user and the spear-phishing email is routed tothe multilayer deception system controller or the honey computer by amail server based, at least partially, upon contact informationassociated with the honey profile. The method also can includedetermining if an interaction threshold is satisfied by the interaction,and in response to determining that the interaction threshold issatisfied, determining that the interaction corresponds to the attack,triggering an alarm indicating that the attack is in progress, blockingthe attack, and propagating information relating to the attack to afurther entity within the private network. The method also can includedetermining if the threshold is to be adjusted based, at leastpartially, upon a determination that the alarm includes a false alarm.

According to another aspect of the concepts and technologies disclosedherein, a multilayer deception system controller is disclosed. Themultilayer deception system controller can include a processorconfigured to execute computer-executable instructions stored in amemory to execute a method including identifying a real user as a targetof an electronic attack and generating a honey profile for a honey user.The honey profile can include a first version of contact informationthat differs from a second version of contact information associatedwith the real user. The method executed by the multilayer deceptionsystem controller also can include generating a honey file, and aninstance of honey activity between a computer operating on the privatenetwork and the honey file, exposing the honey profile on a publicnetwork, detecting an interaction with the honey file, and determining,based upon detecting the interaction with the honey file, if theinteraction corresponds to the electronic attack.

According to some embodiments, the processor is further configured toexecute the computer-executable instructions to upload the honey profileto a social networking server accessible via the public network. In someembodiments, the processor is further configured to execute thecomputer-executable instructions to instruct a mail server associatedwith the private network to route communications directed to an emailaddress associated with the honey profile to a honey computer or to amultilayer deception system controller. The processor also can beconfigured to execute the computer-executable instructions to trigger analarm in response to determining that the interaction corresponds to theelectronic attack. According to some implementations, the processor isfurther configured to execute the computer-executable instructions totrigger an alarm, in response to detecting the interaction with thehoney file, analyze the interaction to determine if an interactionthreshold is satisfied by the interaction, and in response todetermining that the interaction threshold is satisfied, determine thatthe interaction corresponds to the attack, block the attack, andpropagate information relating to the attack to a further entity withinthe private network.

According to another embodiment, the processor is further configured toexecute the computer-executable instructions to trigger an alarm, inresponse to detecting the interaction with the honey file, to analyzethe interaction to determine if an interaction threshold is satisfied bythe interaction, to determine that that the threshold is to be adjustedbased, at least partially, upon determining that the threshold issatisfied and determining that the interaction does not correspond tothe attack, and to adjust the threshold. The processor also can beconfigured to execute the computer-executable instructions to upload thehoney profile to a social networking server accessible via the publicnetwork. The social networking server can be configured to store socialnetworking data including a profile associated with the real user.

According to yet another aspect, a computer storage medium is disclosed.The computer storage medium has computer-executable instructions storedthereon that, when executed by a multilayer deception system controller,cause the multilayer deception system controller to execute a methodincluding determining that a real user of a private network is a targetof an attacker, generating a honey user and a honey profile for thehoney user, the honey profile including a first version of contactinformation that differs from a second version of contact informationassociated with a real profile of the real user, exposing the honeyprofile outside of a private network associated with the real user,hosting a honey file at the private network, generating an instance ofhoney activity between a computer operating on the private network andthe honey file, detecting an interaction with the honey file, anddetermining, based upon detecting the interaction with the honey file,if the interaction corresponds to an attack by the attacker.

In some embodiments, the honey profile is exposed by uploading the honeyprofile to a social networking server accessible via the public network.The social networking server can be configured to store socialnetworking data including the real profile. According to variousembodiments, the computer storage medium further includescomputer-executable instructions that, when executed by the multilayerdeception system controller, cause the multilayer deception systemcontroller to instruct a mail server operating in communication with theprivate network to route a message intended for an email addressassociated with the honey profile to the computer, wherein the computerincludes a honey computer or a multilayer deception system controller,to detect routing of the message to the honey computer, to analyze themessage to determine if the message includes the attack, and to triggeran alarm, in response to determining that the message includes theattack. In some embodiments, the computer storage medium furtherincludes computer-executable instructions that, when executed by themultilayer deception system controller, cause the multilayer deceptionsystem controller to block the attack, and propagate informationassociated with the attack to other entities associated with the privatenetwork.

Other systems, methods, and/or computer program products according toembodiments will be or become apparent to one with skill in the art uponreview of the following drawings and detailed description. It isintended that all such additional systems, methods, and/or computerprogram products be included within this description, be within thescope of this disclosure, and be protected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram illustrating an illustrative operatingenvironment for the various embodiments disclosed herein.

FIG. 2 is a flow diagram showing aspects of a method for providing amultilayer deception system, according to an illustrative embodiment.

FIG. 3 is a flow diagram showing aspects of a method for creating honeyentities, according to another illustrative embodiment.

FIG. 4 is a flow diagram showing aspects of a method for managing falsealarms in a multilayer deception system, according to anotherillustrative embodiment.

FIG. 5 schematically illustrates a network, according to an illustrativeembodiment.

FIG. 6 is a block diagram illustrating an example computer systemconfigured to provide a verification service, according to someillustrative embodiments.

DETAILED DESCRIPTION

The following detailed description is directed to multilayered deceptionfor intrusion detection and prevention. According to various embodimentsof the concepts and technologies disclosed herein, a multilayerdeception system controller operates on a private network. The privatenetwork can be configured to communicate with or can be accessible via apublic network such as the Internet. An attacker may identify a userassociated with the private network as a target for an electronicattack. The multilayer deception system controller is configured toidentify possible or probable targets of electronic attacks and toprotect the targets from exploitation using one or more honey entities.

In some embodiments, the multilayer deception system controlleridentifies a target and generates a honey user and a honey profile forthe honey user. The honey profile can be based, at least partially, upona real profile for the real user. As such, an attacker viewing the honeyprofile can mistake the honey user for the real user. The honey profileis exposed to public network, for example, by uploading the honeyprofile to a social networking site, by publishing documents such asbusiness cards with information from the honey profile, and/or via othermechanisms. As such, attackers may target attacks at the honey userinstead of the real user, thereby providing a first layer of deceptionand protection for the real user and his or her associated resources.The multilayer deception system controller also is configured togenerate various honey entities for emulating and/or otherwiseobfuscating a computing environment associated with the real user. Thehoney entities can include honey computers, honey files and folders,honey servers, and/or honey databases.

The multilayer deception system controller also can generate honeyactivity between the honey entities to further deceive maliciousattackers and/or attacks. The honey entities and honey activity can behosted and/or executed by dedicated real or virtual resources, or hostedby resources associated with real entities such as a computer, server,database, files and folders, and the like. When an attacker targets areal user or a honey user identified via the honey profile, the attackcan be blocked by the various layers of protection provided by the honeyentities. In addition to the layer of protection afforded by the honeyuser, the honey entities can provide other layers of protection. Forexample, an email address exposed in the honey profile can automaticallybe routed to the honey computer or to the multilayer deception systemcontroller.

In other embodiments, attacks that reach the real user and/or his or herassociated resources can be tricked into attacking the various honeyentities instead of real resources. For example, malicious code may befooled by the honey activity into focusing on honey folders, honeyfiles, honey databases, and/or honey servers instead of, or in additionto, the real files, folders, databases, and/or servers. The honeyentities thus can be used to identify and/or isolate the attack fromother entities in the network including, for example, the real entitiesassociated with the real user. In some embodiments, any access detectedwith respect to the honey entities can trigger an alarm condition and/orcan be interpreted as an attack. The multilayer deception systemcontroller can be configured to generate and track alarm conditionsand/or to modify access thresholds that can be used to identify activityas malicious or legitimate.

While the subject matter described herein is presented in the generalcontext of program modules that execute in conjunction with theexecution of an operating system and application programs on a computersystem, those skilled in the art will recognize that otherimplementations may be performed in combination with other types ofprogram modules. Generally, program modules include routines, programs,components, data structures, and other types of structures that performparticular tasks or implement particular abstract data types. Moreover,those skilled in the art will appreciate that the subject matterdescribed herein may be practiced with other computer systemconfigurations, including hand-held devices, multiprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like.

Referring now to FIG. 1, aspects of an operating environment 100 forvarious embodiments of the concepts and technologies disclosed hereinfor a verification service for providing data delivery with senderverification will be described, according to an illustrative embodiment.The operating environment 100 shown in FIG. 1 includes an attacker 102.The attacker 102 can use, or can be, a device operating in communicationwith a public communications network (“public network”) 104. Becauseelectronic attacks are generally launched using electronic devices, theattacker 102 refers to the user and/or a user device utilized by theattacker to launch an attack 108 on a target. It should be understoodthat this embodiment is illustrative, and should not be construed asbeing limiting in any way.

As mentioned above, the attacker 102 resides on or makes use of theprivate network 106. According to embodiments, the functionality of thepublic network 104 can be provided, for example, by the Internet, byother wide area networks (“WAN”), and/or by other networks. It should beunderstood that the public network 104 may or may not be accessible tothe general public. Rather, as used herein a “public network” such asthe public network 104 can include any network that is accessible to theattacker 102 in addition to a target of the attacker 102, as will bemore clearly understood below.

According to various embodiments, a private network 106 exists incommunication with and/or is accessible via the public network 104.According to implementations, the functionality of the private network106 is provided by an intranet, a personal area network (“PAN”), a LocalArea Network (“LAN”), or other limited access network. In someembodiments, the functionality of the private network 106 is provided bya virtual private network (“VPN”) that can use and/or rely upon thepublic network 104 to grant users access. As such, for purposes ofunderstanding the concepts and technologies disclosed herein, it shouldbe understood that the public network 104 includes a network accessibleto the attacker 102 and a target of the attacker 102, and the privatenetwork 106 includes a network accessible only to the target, but notthe attacker 102. It should be understood that this embodiment isillustrative, and should not be construed as being limiting in any way.

According to some implementations of the concepts and technologiesdisclosed herein, the operating environment 100 also includes a socialnetworking server 110 (“SN server”) operating on or in communicationwith the public network 104. The SN server 110 can be configured toexecute a social networking application 112 (“SN application”) toprovide social networking services to users and devices accessing the SNserver 110 via the public network 104. According to variousimplementations of the concepts and technologies disclosed herein, thesocial networking services provided by the SN server 110 include, butare not limited to, the FACEBOOK social networking service, the LINKEDINprofessional networking service, the TWITTER messaging service, othersocial networking services, or the like. In other embodiments, socialnetworking functionality is provided by other services, sites, and/orproviders that are not necessarily known as social networking serviceproviders. As such, the functionality of the SN server 110 should beunderstood as including various services, sites, and/or applicationsthat enable or allow users to interact via email, comment threads,ratings and reviews, messages, chat services, gameplay, bloggingservices, microblogging services, or other mechanisms. As such, itshould be appreciated that the above list of social networking servicesis not exhaustive, as numerous social networking services are notdescribed herein.

According to implementations, the SN application 112 generates and/orhosts social networking data 114 (“SN data”) associated with one or moreusers. The SN data 114 describes, for example, social networkingconnections associated with users; user content such as status updates,reviews, photographs, links, and the like; contact and biographicalinformation associated with users; usage history and statistics; likesand dislikes; comments; connection requests; or the like. According tovarious embodiments, the SN data 114 includes a number of user profiles.The profiles can include name information, contact information, resumeinformation, company and title information, responsibilities of users,other information, or the like. As shown in FIG. 1, the SN data 114includes, in some embodiments, a real profile for a user, denoted asP_(r), and a honey profile for a user, denoted as P_(h).

As shown in FIG. 1, the real profile P_(r) can include a name, contactinformation, company information, and other data. The honey profileP_(h) can include the same information. As shown, however, the name andcontact information for the user associated with the real profile P_(r)and honey profile P_(h) can differ. In particular, as will be explainedin greater detail below, particularly with reference to FIGS. 2-4, thehoney profile P_(h) can include contact information associated with amultilayered deception scheme. The honey profile P_(h) thus can be usedto provide a first layer of protection from attacks 108 by tricking anattacker 102 into attacking an entity associated with the honey profileP_(h) instead of, or in addition to, attacking an entity associated withthe real profile P_(r). These and other aspects of the honey profileP_(h) are described in more detail below.

According to various implementations, the operating environment 100includes a multilayer deception system controller 116 that operates as apart of or in communication with the private network 106. According tovarious embodiments, the multilayer deception system controller 116 alsocan access the public network 104 via the private network 106. Thefunctionality of the multilayer deception system controller 116 can beprovided by one or more server computers, virtual server computers,and/or other real or virtual computing resources. According to variousimplementations, the multilayer deception system controller 116 stores,executes, and/or hosts a multilayer deception system controllerapplication (not shown in FIG. 1) for providing the functionalitydescribed herein for a multilayer deception system.

The operating environment also includes a mail server 118. The mailserver 118 is configured to deliver messages, attachments, and/or otherdata to one or more mail recipients within the private network 106, andto send mail, attachments, and/or other data from users within theprivate network 106 to the public network 104 and/or other systems,networks, and/or devices. As such, the mail server 118 is exposed, invarious embodiments, to the public network 104 to enable the mail server118 to communicate with the public network 104. It should be understoodthat this embodiment is illustrative, and should not be construed asbeing limiting in any way.

In the embodiment illustrated in FIG. 1, various entities exist withinor in communication with the private network 106. For example, theoperating environment 100 includes various resources that can be used bya user, denoted in FIG. 1 as U_(r). For example, the user U_(r) can usea computer 120 for various purposes. According to various embodiments,the user U_(r) interacts with files and folders 122, a server 124,and/or data stores or databases (“database”) 126 in communication withthe computer 120 on the private network 106. As shown in FIG. 1, theuser U_(r) can interact with these and other resources by way ofactivity A_(r). The activity A_(r) of the user U_(r) may include openingfiles stored as the files and folders 122, accessing applications,scripts, and/or programs hosted by the server 124, and/or runningqueries against and/or accessing data stored by the database 126. Itshould be understood that other activity that is related to business orpersonal affairs of the user U_(r) can be conducted on or through theprivate network 106. As such, it should be understood that the aboveexamples of the activity A_(r) are illustrative, and should not beconstrued as being limiting in any way.

The attacker 102 can identify the user U_(r) as a target, and can launchan attack 108 against the user U_(r). According to some embodiments, theattack 108 includes an advanced persistent threat (“APT”) whereby theattacker 102 targets the user U_(r). APT attacks or other forms ofintrusion attacks may begin with a single spear-phishing email or othermechanism for infecting a computer used by the user U_(r), in this case,the computer 120. For purposes of describing the concepts andtechnologies disclosed herein, the disclosure herein describes theattack 108 as beginning with a spear-phishing email targeted at the userU_(r). Because the attack 108 can begin using other mechanisms, itshould be understood that this embodiment is illustrative, and shouldnot be construed as being limiting in any way.

In the above embodiment, wherein the attack 108 commences with aspear-phishing email, the email is routed to the mail server 118, andfrom there to the computer 120. The attack 108 can include key loggersand/or other sophisticated mechanisms for logging and/or repeating theactivity A_(r) performed by the computer 120. As such, the attack 108can compromise data stored in the files and folders 122, applications,programs, and/or other information hosted by the server 124; and/ordata, queries, and/or results from interactions with the database 126.It should be understood that this embodiment is illustrative, and shouldnot be construed as being limiting in any way.

As will be described in more detail herein, particularly with referenceto FIGS. 2-4, the multilayer deception system controller 116 isconfigured, via execution of various application programs such as anmultilayer deception system controller application (not shown in FIG. 1)to provide, manage, and control a multilayered deception system foravoiding, mitigating, and/or blocking advanced persistent threat attacksand/or other attacks 108 targeted at users of the private network 106.The multilayer deception system includes, for example, creation andmanagement of various honey entities that can be executed by the users'resources and/or by other resources on the private network 106. As willbe more clearly understood below, the honey entities can therefore beused to trap the attacks 108 that reach the user U_(r) and/or to deflectattacks from the resources associated with the user U_(r) to the varioushoney entities.

As used herein, entities modified by the word “honey” include virtual orreal entities that emulate and/or appear to provide real functionalityassociated with their non-honey counterparts. The honey entities can beused to deceive an attacker 102 and/or software included in an attack108. Thus, for example, a honey user U_(h) can include a virtual personprovided by software and/or other functionality. While the honey userU_(h) is not a real entity, the honey user U_(h) can appear to be a realentity to the attacker 102 and/or the attack 108. As such, in someinstances the attack 108 is occupied by the honey user U_(h) and/or“resources” associated with the honey user U_(h), which actually arehoney entities, instead of the real user U_(r). In other instances, thehoney entities are executed by resources associated with the real userU_(r) to trap the attacks 108 before the attacks 108 exploit theresources. These and other aspects of the honey entities are describedin more detail below.

According to embodiments, the honey entities include, but are notlimited to, a honey computer 128, honey files and folders 130, a honeyserver 132, a honey database 134, and the honey profile P_(h) mentionedabove with regard to the SN data 114. The multilayer deception systemcontroller 116 also can create, manage, and expose honey activity A_(h)between the honey computer 128, the honey files and folders 130, and/orthe honey database 134. While the various honey entities are illustratedas being separate from the real entities, it should be understood thatthe honey entities can be executed by software on the computer 120. Eachof these honey entities is now described in additional detail.

The honey computer 128 can include a real or virtual computer thatappears, to an attacker 102 or software included in the attack 108, tobe a computer or computing resource belonging to the user U_(r). In someembodiments, the functionality of the honey computer 128 is omitted, andthe multilayer deception techniques disclosed herein rely upon usage ofthe computer 120 instead of, or in addition to, the honey computer 128.In yet other embodiments, the honey computer 128 is omitted, but thefunctionality of the honey computer 128 as described herein is providedby the computer 120. In other embodiments, such as the embodimentillustrated in FIG. 1, the honey computer 128 is a real or virtualcomputer that is provided to insulate the computer 120 from the attacker102. Because the honey computer 128 can be omitted in variousembodiments, it should be understood that this embodiment isillustrative, and should not be construed as being limiting in any way.

The honey computer 128 can provide a layer of protection against theattacks 108 and can operate in conjunction with, or independently of,the honey files and folders 130, the honey server 132, and/or the honeydatabases 134. The honey computer 128 can provide real or virtualresources that appear, to an attacker 102 or attack 108, to be identicalto the computer 120. For example, the honey computer 128 can access thehoney server 132, the honey files and folders 130, the honey database134, and/or other resources via honey activity A_(h). In someembodiments, the mail server 118 is configured, via instructions issuedby the multilayer deception system controller 116, to route email orother messages directed to the honey profile P_(h) to the honey computer128 or to the multilayer deception system controller 116 instead of thecomputer 120. Thus, spear-phishing emails, malicious scripts and/ormacros, as well as other malicious content directed to the honey profileP_(h) can be directed to the honey computer 128 instead of the computer120. In other embodiments, as mentioned above, the honey computer 128 isomitted and emails directed to the honey profile P_(h) are either routedto the multilayer deception system controller 116 or are not routedanywhere and instead are deflected from real users U_(r) by way of thehoney profile P_(h). In some embodiments, the honey profile P_(h)includes an email address that is not associated with any person oruser. In yet other embodiments, as shown in FIG. 1, the email addressincluded in the honey profile P_(h) is associated with the honey userU_(h) and can be, but is not necessarily, directed to the honey computer128 upon receipt by the mail server 118. It should be understood thatthis embodiment is illustrative, and should not be construed as beinglimiting in any way.

The honey files and folders 130 can provide another layer of protectionagainst the attacks 108 and can operate in conjunction with, orindependently of, the honey computer 128, the honey server 132, and/orthe honey databases 134. The honey files and folders 130 can includefalse files and/or folders provided by real or virtual resources withinthe private network 106. As noted above, the honey files and folders 130can be provided by the computer 120. The honey files and folders 130 donot include any information that legitimate users need or desire toaccess. As such, the multilayer deception system controller 116 can beconfigured to monitor the honey files and folders 130 for any access byany entity. Any access of honey files and folders 130 can be understoodby the multilayer deception system controller 116 as being prompted by ahacker or other attack 108. As such, the multilayer deception systemcontroller 116 can be configured to trigger one or more alarms upondetection of any operations on the honey files and folders 130including, but not limited to, reading, opening, moving, copying, orotherwise accessing the honey files and folders 130. The honey files andfolders 130 can be stored on the honey computer 128 and/or on realcomputers, mobile phones, or other resources associated with a real userU_(r). As such, in some embodiments, the honey files and folders 130 arestored on the computer 120 and monitored by software running on thecomputer 120 and/or the multilayer deception system controller 116. Itshould be understood that these embodiments are illustrative, and shouldnot be construed as being limiting in any way.

The honey server 132 can provide another layer of protection against theattacks 108 and can operate in conjunction with, or independently of,the honey computer 128, the honey files and folders 130, and/or thehoney databases 134. The honey server 132 can include one of two typesof real or virtual server computers or other resources. In someembodiments, the honey server 132 is configured to store and host onlyfake or false data such as applications, web pages, and the like. Thus,the multilayer deception system controller 116 can monitor the honeyserver 132, or the honey server 132 can be configured to self-report tothe multilayer deception system controller 116, if any access isdetected at the honey server 132. Access can include any access of thehoney server 132, any connection attempt including an SSH or FTPattempt, or other interactions with the honey server 132. Again, asnoted above, the functionality of the honey server 132 can be providedby the real resources discussed above including, but not limited to, thecomputer 120.

In some embodiments, for example, the functionality of the honey server132 is provided by real or virtual resources used to provide the server124. Thus, the honey server 132 can be provided by the same hardwareused to provide the server 124. As such, the honey server 132 can beconfigured to trap attacks 108 that reach the real user U_(r) and/orresources associated with the real user U_(r) by trapping the attacks108 when the attacks 108 try to access the honey server 132. In someembodiments, the honey server 132 runs a false alarm reduction algorithmfor differentiating between honey activity A_(h) with the honey server132 and activity associated with the attack 108. As such, the honeyserver 132 can be configured to reduce false alarms caused by the honeyactivity A_(h) described below. The reduction of false alarms on thesecond type of honey server 132 is described in more detail below, atleast with regard to FIG. 4.

The honey database 134 can provide another layer of protection againstthe attacks 108 and can operate in conjunction with, or independentlyof, the honey computer 128, the honey files and folders 130, and/or thehoney server 132. The honey database 134 can include fake databasesand/or fake tables, fake rows, fake columns, and/or other fake databasecomponents in a real database such as the database 126. In someembodiments, the honey database 134 is housed by the database 126 and/orthe computer 120. In other embodiments, the honey database 134 isprovided by a real or virtual resource remote from the computer 120and/or database 126 to insulate the computer 120 and/or database 126from the attack 108. The honey database 134 can be monitored by themultilayer deception system controller 116 to detect access to the fakedatabase and/or fake database components. The multilayer deceptionsystem controller 116 can be configured to trigger one or more alarmsupon detecting any activity at the honey database 134.

The honey profile P_(h) mentioned above with regard to the SN data 114can provide another layer of protection against the attacks 108 and canoperate in conjunction with, or independently of, the honey computer128, the honey files and folders 130, the honey server 132, and/or thehoney databases 134. The honey profile P_(h) can include profiles forhoney users such as the honey user U_(h). The honey profile P_(h) canmirror all or most of a real profile P_(r) of the real user U_(r),though some changes can be made. For example, in some embodiments, thehoney profile P_(h) is identical to a real profile P_(r) of the realuser U_(r), except for name and contact information, which may bechanged. Thus, an attacker 102 who identifies the honey profile P_(h) asa target of an attack 108 can direct a spear-phishing email, phishingSMS message, code, links, executables, script, macros, or otherpotentially malicious content to the honey user U_(h). Thus, the honeyprofile P_(h) can be used to deflect attacks from the real user U_(r) toa non-existent, and therefore safe, honey user U_(h). In someembodiments, the mail server 118 can be configured to directcommunications intended for the honey user U_(h) to the honey computer128 for management of the threat, though this is not necessarily thecase.

The honey activity A_(h) can provide yet another layer of protectionagainst the attacks 108 and can operate in conjunction with, orindependently of, the honey computer 128, the honey files and folders130, the honey server 132, the honey databases 134, and/or the honeyprofile P_(h). The honey activity A_(h) can include activity generatedby the multilayer deception system controller 116. The honey activityA_(h) appears to be real traffic generated by a real user U_(r), but isactually real or virtual traffic generated by the multilayer deceptionsystem controller 116 between the honey computer 128 and the other honeyentities shown in FIG. 1, or between the computer 120 and the varioushoney entities shown in FIG. 1. More particularly, as explained above,the honey computer 128 can be eliminated in some embodiments, and thehoney activity A_(h) therefore can originate at the computer 120 orother device (not shown) instead of, or in addition to, the honeycomputer 128.

The honey activity A_(h) includes any traffic corresponding to anyactivity that may be undertaken by the real user U_(r). Thus, the honeyactivity A_(h) may correspond to interactions with remote servers and/orlocal servers such as the honey server 132 and/or the server 124. Thehoney activity A_(h) also can be created to intercept and/or remediatesophisticated malware attacks such as key loggers, and the like. Inparticular, the honey activity A_(h) can obfuscate real keystrokes byproviding additional strokes that may be logged by the attack 108 andfollowed during the exploitation phase of the attack. It should beunderstood that this embodiment is illustrative, and should not beconstrued as being limiting in any way.

In practice, the concepts and technologies disclosed herein provide amultilayer deception system that is controlled and/or orchestrated bythe multilayer deception system controller 116. The multilayer deceptionsystem controller 116 is configured to create and manage honey entities,as well as to monitor and trigger alarms based upon activity with or bythe honey entities by other honey entities and/or by real resources. Themultilayer deception system controller 116 can be configured todetermine a possible target of the attack 108. The target can includehigh-level employees of an organization or other entities or userswithin an organization that may be targeted by the attacker 102. Themultilayer deception system controller 116 is configured to create ahoney user U_(h) that approximates or mirrors the expected target of theattack 108. As part of creating the honey user U_(h), the multilayerdeception system controller 116 can be configured to create a honeyprofile P_(h) that can be exposed to the public to attract or distractthe attacker 102. The attacker 102 may direct attacks against the honeyuser U_(h) instead of, or in addition to, the real user U_(r), andtherefore can provide a first layer of protection for the real userU_(r) and his or her resources.

The multilayer deception system controller 116 also can be configured tocreate honey entities such as, for example, the honey computer 128, thehoney files and folders 130, the honey server 132, the honey database134, and/or the honey activity A_(h). As explained above, these andother honey entities can be provided by dedicated real and/or virtualresources of the private network 106 and/or can be hosted by realentities associated with the real user U_(r) such as the computer 120,the files and folders 122, the server 124, and/or the database 126. Themultilayer deception system controller 116 also can create honeyactivity A_(h) between the various honey entities and/or real resources,if desired. Thus, the multilayer deception system controller 116 cancreate a multilayer deception system including fake users, fakeentities, fake activity between the entities and/or real entities, andeven a fake profile, each of which can independently and/or collectivelyentice attackers 102 to target the fake entities instead of the realentities. Furthermore, even if an attack 108 successfully targets a realentity, the honey entities can be used to trap malicious activity byredirecting the malicious activity from real resources to the honeyentities.

According to various embodiments, the attacker 102 launches an attack108 against the honey user U_(h). The attack 108 can originate via emailor other messaging mechanisms such as SMS, and the like. The privatenetwork 106 can be configured to forward messages and/or other contentto a honey computer 128 or other device for analysis and/or monitoring.In some embodiments, the private network 106 includes a mail server 118that forwards messages for the honey user U_(h) to the multilayerdeception system controller 116 for analysis and/or to the honeycomputer 128 for monitoring. The multilayer deception system controller116 is configured to block the attack 108 and to propagate informationabout the attack 108 to other devices or nodes within the privatenetwork 106 such as, for example, firewalls, blacklists, and the like.As such, the multilayer deception system controller 116 can blockattacks 108 that target the honey user U_(h).

In some embodiments, the multilayer deception system controller 116 alsois configured to monitor the honey entities to reduce false alarms thatmay be triggered by the honey activity A_(h). In some embodiments, themultilayer deception system controller 116 monitors the honey entities.When the multilayer deception system controller 116 detects aninteraction with one or more of the honey activities, the multilayerdeception system controller 116 can determine if a threshold is met. Thethreshold can be defined by the multilayer deception system controller116 and can specify, for example, times and/or activity and/orcombinations of activity that are associated with the honey activityA_(h) and/or normal activity of the user U_(r). If the activity detectedby the multilayer deception system controller 116 satisfies one or morespecified thresholds, the multilayer deception system controller 116 candetermine that the detected interaction corresponds to an attack 108. Ifthe activity is not satisfy one or more specified thresholds, themultilayer deception system controller 116 can determine that thedetected interaction is associated with the honey activity A_(h).

If the multilayer deception system controller 116 determines that anattack 108 is underway, the multilayer deception system controller 116can trigger an alarm. The multilayer deception system controller 116also can determine if a threshold adjustment process should be executed.The multilayer deception system controller 116 can determine that thethreshold adjustment process is to be completed each time an alarm isreceived, if an alarm is determined to be false, or at other times. Ifthe multilayer deception system controller 116 determines that thethreshold adjustment process is to be completed, the multilayerdeception system controller 116 can adjust the threshold(s) and managealarms, if desired. These and other aspects of the multilayer deceptionsystem controller 116 are described in more detail below, at least withreference to FIGS. 2-4.

FIG. 1 illustrates one attacker 102, one public network 104, one privatenetwork 106, one SN server 110, one multilayer deception systemcontroller 116, and single instances of the real and honey entities. Itshould be understood, however, that various implementations of theoperating environment 100 include multiple attackers 102, multiplepublic networks 104, multiple private networks 106, multiple SN servers110, multiple multilayer deception system controllers 116, and/ormultiple instances of the real and honey entities. As such, theillustrated embodiment should be understood as being illustrative, andshould not be construed as being limiting in any way.

Turning now to FIG. 2, aspects of a method 200 for providing amultilayer deception system will be described in detail, according to anillustrative embodiment. It should be understood that the operations ofthe methods disclosed herein are not necessarily presented in anyparticular order and that performance of some or all of the operationsin an alternative order(s) is possible and is contemplated. Theoperations have been presented in the demonstrated order for ease ofdescription and illustration. Operations may be added, omitted, and/orperformed simultaneously, without departing from the scope of theappended claims.

It also should be understood that the methods disclosed herein can beended at any time and need not be performed in its entirety. Some or alloperations of the methods, and/or substantially equivalent operations,can be performed by execution of computer-readable instructions includedon a computer storage media, as defined herein. The term“computer-readable instructions,” and variants thereof, as used in thedescription and claims, is used expansively hereinto include routines,applications, application modules, program modules, programs,components, data structures, algorithms, and the like. Computer-readableinstructions can be implemented on various system configurationsincluding single-processor or multiprocessor systems, minicomputers,mainframe computers, personal computers, hand-held computing devices,microprocessor-based, programmable consumer electronics, combinationsthereof, and the like.

Thus, it should be appreciated that the logical operations describedherein are implemented (1) as a sequence of computer implemented acts orprogram modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system. The implementation is a matter of choice dependent onthe performance and other requirements of the computing system.Accordingly, the logical operations described herein are referred tovariously as states, operations, structural devices, acts, or modules.These states, operations, structural devices, acts, and modules may beimplemented in software, in firmware, in special purpose digital logic,and any combination thereof.

For purposes of illustrating and describing the concepts of the presentdisclosure, the methods disclosed herein are described as beingperformed by the multilayer deception system controller 116 viaexecution of one or more software modules such as, for example, amultilayer deception system controller application (shown in FIG. 6). Itshould be understood that additional and/or alternative devices and/ornetwork nodes can provide the functionality described herein viaexecution of one or more modules, applications, and/or other softwareincluding, but not limited to, the multilayer deception systemcontroller application. Thus, the illustrated embodiments areillustrative, and should not be viewed as being limiting in any way.

The method 200 begins at operation 202, wherein the multilayer deceptionsystem controller 116 creates (“generates”) honey entities. As explainedabove with reference to FIG. 1, the honey entities can include a honeyuser U_(h) and/or a honey profile P_(h) that appears to be a legitimateprofile of the honey user U_(h). The honey entities also can include oneor more honey computers 128, one or more honey files and folders 130,one or more honey servers 132, and one or more honey databases 134. Themultilayer deception system controller 116 also can create honeyactivity A_(h), as explained above in detail with reference to FIG. 1.The creation of the honey entities as depicted in FIG. 2 is illustratedand described in more detail below with reference to FIG. 3.

From operation 202, the method 200 proceeds to operation 204, whereinthe multilayer deception system controller 116 activates the honeyentities generated in operation 202. In some embodiments, the multilayerdeception system controller 116 exposes a honey profile P_(h) associatedwith the honey user U_(h). The honey profile P_(h) can be exposed by themultilayer deception system controller 116 by uploading or creating aprofile at a social networking service such as the SN server 110 hostinga SN application 112, by creating a biography on a company website orportal, and/or via other mechanisms. In one contemplated embodiment, ahoney profile P_(h) is exposed by publishing documents electronically orin tangible form with contact information for a honey users U_(h).Because other mechanisms for exposing the honey user U_(h) and/or ahoney profile P_(h) are contemplated, it should be understood that theseembodiments are illustrative, and should not be construed as beinglimiting in any way.

The multilayer deception system controller 116 can activate the otherhoney entities in various ways. In some embodiments, the multilayerdeception system controller 116 creates honey entities on real orvirtual resources that are dedicated to providing the honey entities.Thus, for example, a database, a server, a computer, and/or storagecapacity can be dedicated to providing a honey database 134, a honeyserver 132, a honey computer 128, and/or the honey files and folders130, respectively. In other embodiments, the multilayer deception systemcontroller 116 activates the honey entities by creating the entities onreal resources such as, for example, the computer 120, the server 124,the database 126, and/or by adding the honey files and folders 130 tothe files and folders 122. It should be understood that theseembodiments are illustrative, and should not be construed as beinglimiting in any way.

From operation 204, the method 200 proceeds to operation 206, whereinthe multilayer deception system controller 116 detects an interactionwith one or more of the honey entities created in operation 202.According to various embodiments, the honey entities are hosted by realor virtual resources in communication with the multilayer deceptionsystem controller 116. Thus, the multilayer deception system controller116 can receive reports from the honey entities that indicate if any ofthe honey entities has been accessed or otherwise interacted with. Inother embodiments, the multilayer deception system controller 116monitors activity at the honey activities and therefore can beconfigured to recognize the interaction without any reportingmechanisms. Because the multilayer deception system controller 116 candetect interactions with the honey entities in a number of ways, itshould be understood that this embodiment is illustrative, and shouldnot be construed as being limiting in any way.

From operation 206, the method 200 proceeds to operation 208, whereinthe multilayer deception system controller 116 analyzes the interactionwith the honey entities. In various embodiments, the multilayerdeception system controller 116 is configured to interpret anyinteraction with the honey entities as malicious activity such as anattack 108. Thus, the multilayer deception system controller 116 can beconfigured to analyze the interaction to determine how to recognize theattack 108 if directed to other entities or devices on the privatenetwork 106.

The analysis of operation 208 can include, for example, analyzingmessage headers or other source information associated with theinteraction, determining a signature of malware conducting theinteraction, and/or detecting other functionality associated with theinteraction. In some embodiments, for example, an attack 108 commencesvia a phishing or spear-phishing email. Thus, the analysis of operation208 can include a detailed analysis of an email that was used to launchan attack 108 in which the interaction was detected to store informationrelating to the source, timing, contents, and/or other aspects of theemail. Because attacks 108 can be launched via various mechanisms, andbecause the interaction can include other types of interactions with thehoney entities, it should be understood that this embodiment isillustrative, and should not be construed as being limiting in any way.

From operation 208, the method 200 proceeds to operation 210, whereinthe multilayer deception system controller 116 blocks the attack 108and/or commands other entities on the private network 106 to block theattack 108. The multilayer deception system controller 116 can use theinformation determined in operation 208 to block the attack 108 fromfurther progressing. Thus, for example, the multilayer deception systemcontroller 116 can quarantine the attack 108, order other devices in theprivate network 106 or elsewhere to quarantine the attack, close orrestrict ports to the attack 108, and/or take other actions. Themultilayer deception system controller also can add source informationassociated with the attack 108 to IP blacklists, sender blacklists,firewalls, and/or other mechanisms to prevent future attacks 108 fromthe same attacker 102.

From operation 210, the method 200 proceeds to operation 212, whereinthe multilayer deception system controller 116 propagates an attacksignature determined during remediation of the attack 108 to otherdevices in the private network 106 and/or to other entities outside ofthe private network 106. As such, the multilayer deception systemcontroller 116 can share information associated with the attack 108 withother entities within or remote from the private network 106 to preventfuture attacks. Operation 212 can include, in some embodiments, thefunctionality of operation 210, if desired.

From operation 212, the method 200 proceeds to operation 214. The method200 ends at operation 214.

Turning now to FIG. 3, aspects of a method 300 for creating(“generating”) honey entities will be described in detail, according toan illustrative embodiment. It should be understood that the method 300illustrated in FIG. 3 can, but does not necessarily, correspond toexecution of the operation 202 illustrated in FIG. 2. The method 300begins at operation 302, wherein the multilayer deception systemcontroller 116 identifies a target within or associated with the privatenetwork 106. According to some embodiments, the multilayer deceptionsystem controller 116 identifies, in operation 302, a user U_(r) that isdetermined, by the multilayer deception system controller 116, to be alikely or expected target of an attack 108. The multilayer deceptionsystem controller 116 also can identify one or more computers 120, oneor more files and folders 122, one or more servers 124, and/or one ormore databases 126 that are likely and/or expected to be the target ofthe attack 108. For purposes of describing the concepts and technologiesdisclosed herein, the target is described herein as a user U_(r). Basedon the above description of FIGS. 1-2, it can be appreciated that thisembodiment is illustrative.

The multilayer deception system controller 116 can identify the userU_(r); or in some embodiments the computer 120, files and folders 122,server 124, and/or database 126; based upon activity associated with theuser U_(r). The multilayer deception system controller 116 also canidentify the target based upon historical trends, “best guess” analysis,posted or published threats, and the like. Because numerous approachesare possible and are contemplated for identifying a target, it should beunderstood that these embodiments are illustrative, and should not beconstrued as being limiting in any way.

From operation 302, the method 300 proceeds to operation 304, whereinthe multilayer deception system controller 116 creates (“generates”) ahoney user U_(h). The honey user U_(h), as explained above, can mirroror emulate the user U_(r) identified in operation 302. In particular,the multilayer deception system controller 116 or other entity cancreate a software representation of the user U_(r) and treat thatsoftware representation as the honey user U_(h). Thus, the honey userU_(h) can be used to deceive the attacker 102 to send an attack 108 tothe honey user U_(h) instead of, or in addition to, the real user U_(r).It should be understood that this embodiment is illustrative, and shouldnot be construed as being limiting in any way.

From operation 304, the method 300 proceeds to operation 306, whereinthe multilayer deception system controller 116 creates (“generates”) theother honey entities. According to various embodiments, as can beappreciated from the description of FIG. 1 above, the honey entitiescreated in operation 306 can, but do not necessarily, include one ormore honey computers 128, honey files and folders 130, honey servers132, honey databases 134, and/or other honey entities. As noted above,the honey computer 128 is optional, and therefore can be omitted, ifdesired, or the functionality thereof can be provided by the computer120.

From operation 306, the method 300 proceeds to operation 308, whereinthe multilayer deception system controller 116 creates (“generates”) thehoney activity A_(h). The honey activity A_(h) can include activitybetween the various honey entities created in operation 306. In someembodiments, the honey activity A_(h) originates at the computer 120 andterminates at the various honey entities generated in operation 304. Inother embodiments, the honey activity A_(h) originates and terminateswithin the various honey entities generated in operation 304. The honeyactivity A_(h) can emulate real activity A_(r) of the user U_(r). Thus,if the attack 108 is successfully routed to the real resources and thehoney entities, the attack 108 can monitor and/or report the honeyactivity A_(h) instead of searching for and/or identifying the realactivity A_(r). Also, the attack 108 can be tricked into attacking honeyentities instead of the real entities based upon detecting the honeyactivity A_(h), Thus, the honey activity can add a layer of obfuscationto the multilayer deception system by way of including fake activity todeceive attackers 102 and/or attacks 108.

In some embodiments, the honey activity A_(h) includes, but is notlimited to, activity representing accessing the honey files and folders130. Thus, the honey activity A_(h) can include activity originating atthe computer 120 and/or the honey computer 128 and terminating at one ormore of the honey files and folders 130. In other embodiments, the honeyactivity A_(h) includes accessing the honey servers 132 and/or the honeydatabase 134. Other activities can be embodied by the honey activityA_(h). The honey activity A_(h) can appear, to the attacker 102 and/orthe attack 108, to be legitimate activity of the user U_(r). In reality,however, the honey activity A_(h) can include interactions with honeyentities that, if repeated by the attack 108, trigger alarms, reveallittle or no sensitive data, and/or can be contained by the multilayerdeception system controller 116.

From operation 308, the method 300 proceeds to operation 310, whereinthe multilayer deception system controller 116 generates a honey profileP_(h). As explained above in detail with reference to FIG. 1, the honeyprofile P_(h) can correspond to the honey user U_(h) created inoperation 304. The honey profile P_(h) can include biographical and/orprofessional information that mirrors, emulates, and/or is evenidentical to a real profile P_(r) of the user U_(r). As such, anattacker 102 reviewing the honey profile P_(h) may identify the honeyuser U_(h) as a target for an attack 108. Thus, the multilayer deceptionsystem controller 116 can remediate or redirect attacks 108 from theattacker 102, as explained above with reference to FIGS. 1-2.

From operation 310, the method 300 proceeds to operation 312. The method300 ends at operation 312.

Turning now to FIG. 4, aspects of a method 400 for managing false alarmsin a multilayer deception system will be described in detail, accordingto an illustrative embodiment. In some embodiments, the functionalitydescribed herein with reference to FIG. 4 can be, but is notnecessarily, provided by the multilayer deception system controller 116during execution of the operations 206-208 of FIG. 2. The method 400begins at operation 402, wherein the multilayer deception systemcontroller 116 monitors the honey entities.

As explained above, in some embodiments the multilayer deception systemcontroller 116 is configured to monitor traffic originating orterminating at any of the honey entities. In other embodiments, themultilayer deception system controller 116 is configured to receivereports from the honey entities indicating any activity or interactionsat the honey activity. In yet other embodiments, the honey activitiescorrespond to fake entities, and as such, any interactions with thehoney entities can be determined to be malicious. In yet anotherembodiment, the mail server 118 is configured to inform the multilayerdeception system controller 116 if an email is received for an emailaddress included in a honey profile P_(h). Because the multilayerdeception system controller 116 can monitor the honey entities in anumber of ways not described herein, it should be understood that theseembodiments are illustrative, and should not be construed as beinglimiting in any way.

From operation 402, the method 400 proceeds to operation 404, whereinthe multilayer deception system controller 116 determines if a honeyentity has been accessed. In some embodiments, the multilayer deceptionsystem controller 116 pauses execution of the method 400 until one ofthe honey entities is accessed. In other embodiments, as shown in FIG.4, if the multilayer deception system controller 116 determines, inoperation 404, that one or more of the honey entities has not beenaccessed or otherwise interacted with, the method 400 can return tooperation 404. It should be understood that this embodiment isillustrative, and should not be construed as being limiting in any way.

If the multilayer deception system controller 116 determines, inoperation 404, that one or more of the honey entities has been accessedor otherwise interacted with, the method 400 proceeds to operation 406.In operation 406, the multilayer deception system controller 116determines if an access threshold is satisfied. As explained above withreference to FIG. 1, the multilayer deception system controller candefine thresholds for access. The thresholds can define types, times,and/or other aspects of activity with the honey entities that aretolerated and/or expected. For example, the thresholds can be configuredto prevent or reduce the probability that the honey activity A_(h) willtrigger an alert or alarm.

The thresholds can define, for example, times of day at whichinteractions with the honey entities indicate or do not indicate anattack 108, frequency of activity that indicates or does not indicate anattack 108, and/or the like. In some embodiments, the thresholds specifythat any access or interaction with some honey entities indicate anattack 108. These thresholds can be defined by users and/or by themultilayer deception system controller 116.

If the multilayer deception system controller 116 determines, inoperation 406 that an access threshold is not satisfied for the activityor interaction detected in operation 404, the method 400 can return tooperation 404, and the multilayer deception system controller 116 canwait for another interaction. Alternatively, though not illustrated inFIG. 4, the method 400 can end.

If the multilayer deception system controller 116 determines, inoperation 406, that an access threshold is satisfied, the method 400proceeds to operation 408. In operation 408, the multilayer deceptionsystem controller 116 can trigger an alarm. The alarm can be used byother entities, devices, or nodes to remediate the attack 108 and/or forother purposes.

From operation 408, the method 400 proceeds to operation 410, whereinthe multilayer deception system controller 116 determines if a thresholdadjustment is to be made. The multilayer deception system controller 116can determine, based upon an analysis of the interaction detected inoperation 404 that the interaction correspond to honey activity A_(h),for example, or otherwise does not represent malicious activity. In suchembodiments, the multilayer deception system controller 116 candetermine that one or more of the thresholds are to be adjusted. If themultilayer deception system controller 116 determines that the one ormore thresholds are not to be adjusted, the method 400 can end. Althoughnot shown in FIG. 4, the method 400 also can return to operation 404, ifdesired.

If the multilayer deception system controller 116 determines, inoperation 410, that a threshold adjustment is to be made, the operation400 proceeds to operation 412. At operation 412, the multilayerdeception system controller 116 adjusts the thresholds and/or managesalarms generated in operation 408. The multilayer deception systemcontroller 116 can adjust the thresholds to avoid alarm conditions inthe future if the action that triggered the alarm in operation 408 isdetermined not to be malicious. The thresholds can be adjusted to ignorenon-malicious activity and to thereby enhance the performance of themultilayer deception system controller 116 by reducing false alarms.

From operation 412, the method 400 proceeds to operation 414. As notedabove, the method 400 also can proceed to operation 414 if themultilayer deception system controller 116 determines, in operation 410,that no threshold adjustment is to be made. The method 400 ends atoperation 414.

According to various embodiments of the concepts and technologiesdisclosed herein, the multiple layers of deception provided by thevarious honey entities are configured to detect an attack 108 with someprobability at each stage of the attack 108. Each of the honey entitiescan be considered as a layer of the multilayer deception system, canoperate independently and/or in conjunction with one another, and can,but does not necessarily, correspond to real entities. As is generallyunderstood, an attacker 102 often takes multiple steps to launch anattack 108. For example, the attacker 102 first enters a network, theninfects a machine, then exports data, etc. Thus, various embodiments ofthe concepts and technologies disclosed herein provide that even if theattacker 102 manages to avoid one layer of protection provided by themultilayer deception system, e.g., one of the honey entities, anotherlayer or honey entity may catch the attacker 102 at a later phase of theattack 108.

In one contemplated example, an attacker 102 browses a social networkingsite such as a social networking service provided by the SN server 110.The attacker 102 determines that a real user U_(r) works at a company,for example, a company that handles customer data. The attacker 102 maydetermine that the real user U_(r) has specific work experience thatwould most likely include having access to data the attacker 102 wantsto access. The attacker 102 obtains an email address of the user U_(r)and sends a phishing email to the user U_(r). The user U_(r) opens theemail with a computer such as the computer 120, and the computer 120 isinfected with malware remotely controlled by the attacker 102. Fromhere, the attacker 102 is able to monitor electronic activity of theuser U_(r) and may determine that the user U_(r) accesses a specificserver 124, database 126, files and folders 122, and/or other resourceson his computer 120 and/or in communication with the computer 120. Onthe server 124, the attacker 102 may determine that the user U_(r)queries specific databases 126 and/or access data stored at thedatabases 126, in this example, the data on the database 126 can includecustomer data. Thus, the attacker 102 can navigate to the server 124,access the database 126, and exfiltrate some or all of the data.

According to various embodiments of the concepts and technologiesdisclosed herein, the multilayer deception system disclosed hereinprovides multiple layers where the above attack 108 can be avoided,detected, mitigated, and/or blocked. For example, if the profile of theuser U_(r) targeted by the attacker 102 is actually a honey profileP_(h) as disclosed herein, the attacker 102 sends a message to an emailaddress that is being monitored by the multilayer deception systemcontroller 116 instead of the email address of the user U_(r). Thus, theattack 108 can be avoided if the attacker 102 uses the honey profileP_(h) to launch an attack.

If the profile located by the attacker 102 corresponds to a real profileP_(r) of the user U_(r), the attacker 102 may get past the first layerof protection and the computer 120 of the user U_(r) may thus beinfected. Thus, the attack 108 may begin searching the computer 120 tofind what data should be exfiltrated. As such, various embodiments ofthe concepts and technologies disclosed herein include the generationand usage of honey activity A_(h) that obfuscates real activity A_(r) ofthe user U_(r). Furthermore, embodiments include generation andactivation of other honey entities such as the honey files and folders130 on the computer 120 and/or on a honey computer 128 that the malwareassociated with the attack 108 may identify during a random search fordata. Furthermore, the honey activity A_(h) may trick the attack 108into opening one of the honey files and folders 130. Any access of thehoney files and folders 130 may be understood by the multilayerdeception system controller 116 as an attack 108 and can be actedagainst to mitigate or block the attack 108.

In various embodiments, multiple honey servers 132 can also be includedto lure the attacker 102 or attack 108 to connect to an IP addressassociated with the honey servers 132, thereby triggering an alarm.Embodiments also include additional layers of protection that can beprovided by the honey files and folders 130 and/or the honey databases134. Thus, even if the attacker 102 or the attack 108 successfullynavigates to a real server 124, the server 124 can host or connect tothe honey files and folders 130 and/or the honey database 134 to againlure the attacker 102 or attack 108 away from the real files and folders122 and/or database 126.

It can be appreciated from the above description that in someembodiments, each of the honey entities can provide an independent layerof protection. In other embodiments, the honey entities can cooperate toprovide multiple interconnected layers of protection. In variousembodiments, any access of the honey entities described herein cantrigger an alarm.

Although not described in detail above, each of the honey entities caninclude further functionality for providing the various featuresdescribed herein. For example, in some embodiments, each of the honeyentities includes a deception service controller on the device thatprovides the honey entity. The deception service controller isconfigured to manage the honey entity. Thus, for example, if a computer120 hosts honey activity A_(h) and/or honey files and folders 130, thecomputer 120 also can host or execute a deception service controller tomanage these honey entities. According to various embodiments, thedeception service controller on the computer 120 is configured tocommunicate with the multilayer deception system controller 116 in theprivate network 106 that monitors alarms and states of devices on theprivate network 106. The multilayer deception system controller 116 alsocan be configured to push commands to the deception service controllerto add or create honey activity A_(h), a honey database 134, a honeyserver 132, and/or honey files and folders 130.

Turning now to FIG. 5, additional details of the networks 104, 106 areillustrated, according to an illustrative embodiment. The networks 104,106 include a cellular network 502, a packet data network 504, forexample, the Internet, and a circuit switched network 506, for example,a publicly switched telephone network (“PSTN”). The cellular network 502includes various components such as, but not limited to, basetransceiver stations (“BTSs”), Node-B's or e-Node-B's, base stationcontrollers (“BSCs”), radio network controllers (“RNCs”), mobileswitching centers (“MSCs”), mobile management entities (“MMEs”), shortmessage service centers (“SMSCs”), multimedia messaging service centers(“MMSCs”), home location registers (“HLRs”), home subscriber servers(“HSSs”), visitor location registers (“VLRs”), charging platforms,billing platforms, voicemail platforms, GPRS core network components,location service nodes, an IP Multimedia Subsystem (“IMS”), and thelike. The cellular network 502 also includes radios and nodes forreceiving and transmitting voice, data, and combinations thereof to andfrom radio transceivers, networks, the packet data network 504, and thecircuit switched network 506.

A mobile communications device 508, such as, for example, a cellulartelephone, a user equipment, a mobile terminal, a PDA, a laptopcomputer, a handheld computer, and combinations thereof, can beoperatively connected to the cellular network 502. The cellular network502 can be configured as a 2G GSM network and can provide datacommunications via GPRS and/or EDGE. Additionally, or alternatively, thecellular network 502 can be configured as a 3G UMTS network and canprovide data communications via the HSPA protocol family, for example,HSDPA, EUL (also referred to as HSUPA), and HSPA+. The cellular network502 also is compatible with 4G mobile communications standards as wellas evolved and future mobile standards.

The packet data network 504 includes various devices, for example,servers, computers, databases, and other devices in communication withanother, as is generally known. The packet data network 504 devices areaccessible via one or more network links. The servers often storevarious files that are provided to a requesting device such as, forexample, a computer, a terminal, a smartphone, or the like. Typically,the requesting device includes software (a “browser”) for executing aweb page in a format readable by the browser or other software. Otherfiles and/or data may be accessible via “links” in the retrieved files,as is generally known. In some embodiments, the packet data network 504includes or is in communication with the Internet. The circuit switchednetwork 506 includes various hardware and software for providing circuitswitched communications. The circuit switched network 506 may include,or may be, what is often referred to as a plain old telephone system(POTS). The functionality of a circuit switched network 506 or othercircuit-switched network are generally known and will not be describedherein in detail.

The illustrated cellular network 502 is shown in communication with thepacket data network 504 and a circuit switched network 506, though itshould be appreciated that this is not necessarily the case. One or moreInternet-capable devices 510, for example, a PC, a laptop, a portabledevice, or another suitable device, can communicate with one or morecellular networks 502, and devices connected thereto, through the packetdata network 504. It also should be appreciated that theInternet-capable device 510 can communicate with the packet data network504 through the circuit switched network 506, the cellular network 502,and/or via other networks (not illustrated).

As illustrated, a communications device 512, for example, a telephone,facsimile machine, modem, computer, or the like, can be in communicationwith the circuit switched network 506, and therethrough to the packetdata network 504 and/or the cellular network 502. It should beappreciated that the communications device 512 can be anInternet-capable device, and can be substantially similar to theInternet-capable device 510. In the specification, the public network104 is used to refer broadly to any combination of the networks 502,504, 506. It should be appreciated that substantially all of thefunctionality described with reference to the public network 104 can beperformed by the cellular network 502, the packet data network 504,and/or the circuit switched network 506, alone or in combination withother networks, network elements, and the like. Similarly, thefunctionality of the private network 106 can be provided by anycombination of the networks 502, 504, and/or 506

According to various implementations, the attacker 102 can use anycombination of the devices disclosed herein including, but not limitedto, the mobile device 508, the Internet capable device 510, and/or thecommunication device 512 to launch the attack 108 against a target onthe private network 106, to access the SN server 110 to obtain the SNdata 114, to send messages, emails, and/or other attacks 108 to thetarget, and/or for other interactions between the attacker 102 and thetarget. As such, it should be understood that the attacker 102, the SNserver 110, the multilayer deception system controller 116, and/or themail server 118 can interact with one another via any number and/orcombination of devices and/or networks.

FIG. 6 is a block diagram illustrating a computer system 600 configuredto provide the functionality described herein for a multilayer deceptionsystem controller 116, in accordance with various embodiments of theconcepts and technologies disclosed herein. The computer system 600 canbe configured to provide the functionality of any of the softwarecomponents described herein for providing a multilayer deception system.The computer system 600 includes a processing unit 602, a memory 604,one or more user interface devices 606, one or more input/output (“I/O”)devices 608, and one or more network devices 610, each of which isoperatively connected to a system bus 612. The bus 612 enablesbi-directional communication between the processing unit 602, the memory604, the user interface devices 606, the I/O devices 608, and thenetwork devices 610.

The processing unit 602 may be a standard central processor thatperforms arithmetic and logical operations, a more specific purposeprogrammable logic controller (“PLC”), a programmable gate array, orother type of processor known to those skilled in the art and suitablefor controlling the operation of the server computer. Processing unitsare generally known, and therefore are not described in further detailherein.

The memory 604 communicates with the processing unit 602 via the systembus 612. In some embodiments, the memory 604 is operatively connected toa memory controller (not shown) that enables communication with theprocessing unit 602 via the system bus 612. The memory 604 includes anoperating system 614 and one or more program modules 616. The operatingsystem 614 can include, but is not limited to, members of the WINDOWS,WINDOWS CE, and/or WINDOWS MOBILE families of operating systems fromMICROSOFT CORPORATION, the LINUX family of operating systems, theSYMBIAN family of operating systems from SYMBIAN LIMITED, the BREWfamily of operating systems from QUALCOMM CORPORATION, the MAC OS, iOS,and/or LEOPARD families of operating systems from APPLE CORPORATION, theFREEBSD family of operating systems, the SOLARIS family of operatingsystems from ORACLE CORPORATION, other operating systems, and the like.

The program modules 616 may include various software and/or programmodules described herein. In some embodiments, for example, the programmodules 616 include an multilayer deception system controllerapplication 618. This and/or other programs can be embodied incomputer-readable media containing instructions that, when executed bythe processing unit 602, perform one or more of the methods 200, 300,400 described in detail above with respect to FIGS. 2-4. According toembodiments, the program modules 616 may be embodied in hardware,software, firmware, or any combination thereof. Although not shown inFIG. 6, it should be understood that the memory 604 also can beconfigured to store the honey entities and/or other data, if desired.

By way of example, and not limitation, computer-readable media mayinclude any available computer storage media or communication media thatcan be accessed by the computer system 600. Communication media includescomputer-readable instructions, data structures, program modules, orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any delivery media. The term “modulateddata signal” means a signal that has one or more of its characteristicschanged or set in a manner as to encode information in the signal. Byway of example, and not limitation, communication media includes wiredmedia such as a wired network or direct-wired connection, and wirelessmedia such as acoustic, RF, infrared and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

Computer storage media includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, RAM, ROM, Erasable Programmable ROM (“EPROM”),Electrically Erasable Programmable ROM (“EEPROM”), flash memory or othersolid state memory technology, CD-ROM, digital versatile disks (“DVD”),or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to store the desired information and which can beaccessed by the computer system 600. In the claims, the phrase “computerstorage medium” and variations thereof, does not include waves, signals,and/or other transitory and/or intangible communication media, per se.

The user interface devices 606 may include one or more devices withwhich a user accesses the computer system 600. The user interfacedevices 606 may include, but are not limited to, computers, servers,personal digital assistants, cellular phones, or any suitable computingdevices. The I/O devices 608 enable a user to interface with the programmodules 616. In one embodiment, the I/O devices 608 are operativelyconnected to an I/O controller (not shown) that enables communicationwith the processing unit 602 via the system bus 612. The I/O devices 608may include one or more input devices, such as, but not limited to, akeyboard, a mouse, or an electronic stylus. Further, the I/O devices 608may include one or more output devices, such as, but not limited to, adisplay screen or a printer.

The network devices 610 enable the computer system 600 to communicatewith other networks or remote systems via a network, such as the privatenetwork 106 and/or the public network 104. Examples of the networkdevices 610 include, but are not limited to, a modem, a radio frequency(“RF”) or infrared (“IR”) transceiver, a telephonic interface, a bridge,a router, or a network card. The networks 104, 106 may include awireless network such as, but not limited to, a Wireless Local AreaNetwork (“WLAN”) such as a WI-FI network, a Wireless Wide Area Network(“WWAN”), a Wireless Personal Area Network (“WPAN”) such as BLUETOOTH, aWireless Metropolitan Area Network (“WMAN”) such a WiMAX network, or acellular network. Alternatively, the networks 104, 106 may be one ormore, or a combination of wired network such as, but not limited to, aWAN such as the Internet, a LAN, a PAN, a wired Metropolitan AreaNetwork (“MAN”), and/or other networks.

Based on the foregoing, it should be appreciated that systems andmethods for multilayered deception for intrusion detection have beendisclosed herein. Although the subject matter presented herein has beendescribed in language specific to computer structural features,methodological and transformative acts, specific computing machinery,and computer-readable media, it is to be understood that the inventiondefined in the appended claims is not necessarily limited to thespecific features, acts, or media described herein. Rather, the specificfeatures, acts and mediums are disclosed as example forms ofimplementing the claims.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of theembodiments, which is set forth in the following claims.

We claim:
 1. A method comprising: generating, by a processor executing amultilayer deception system controller application, a plurality of honeyentities and an instance of honey activity associated with one honeyentity of the plurality of honey entities at a private network, theplurality of honey entities including a honey profile for a honey user;exposing, by the processor, the honey profile outside of the privatenetwork; detecting, by the processor, an interaction with the one honeyentity of the plurality of honey entities; and analyzing, by theprocessor, the interaction to determine if the interaction correspondsto an attack.
 2. The method of claim 1, further comprising generatingthe honey profile associated with the honey user based, at leastpartially, upon a real profile of a real user associated with theprivate network.
 3. The method of claim 2, wherein the real profilecomprises a first version of contact information, and wherein the honeyprofile comprises a second version of the contact information.
 4. Themethod of claim 3, wherein exposing the honey profile outside theprivate network comprises uploading information associated with thehoney profile to a social networking service.
 5. The method of claim 1,wherein generating the honey entity comprises generating a honey serverat the private network.
 6. The method of claim 1, wherein the instanceof honey activity comprises activity between the honey entity and acomputer operating on the private network.
 7. The method of claim 6,wherein the computer comprises a honey computer isolated from the realuser, wherein the attack comprises a spear-phishing email, and whereinthe spear-phishing email is routed by the mail server to a multilayerdeception system controller that monitors an email address associatedwith the honey profile.
 8. The method of claim 1, further comprising:determining if an interaction threshold is satisfied by the interaction;and in response to determining that the interaction threshold issatisfied, determining that the interaction corresponds to the attack,triggering an alarm indicating that the attack is in progress, blockingthe attack, and propagating information relating to the attack to afurther entity within the private network.
 9. The method of claim 8,further comprising: determining if the threshold is to be adjustedbased, at least partially, upon a determination that the alarm comprisesa false alarm.
 10. A system comprising: a processor; and a memory thatstores computer-executable instructions that, when executed by theprocessor, cause the processor to perform operations comprisingidentifying a real user as a target of an electronic attack, generatinga honey profile for a honey user, the honey profile comprising a firstversion of contact information that differs from a second version ofcontact information associated with the real user, generating a honeyentity, and an instance of honey activity between a computer operatingon a private network and the honey entity, exposing the honey profile ona public network, detecting an interaction with the honey entity, anddetermining, based upon detecting the interaction with the honey entity,if the interaction corresponds to the electronic attack.
 11. The systemof claim 10, wherein the processor executes the computer-executableinstructions to: upload the honey profile to a social networking serveraccessible via the public network.
 12. The system of claim 10, whereinthe processor executes the computer-executable instructions to instructa mail server associated with the private network to routecommunications directed to an email address associated with the honeyprofile to a multilayer deception system controller monitors the emailaddress.
 13. The system of claim 10, wherein the processor executes thecomputer-executable instructions to trigger an alarm, in response todetermining that the interaction corresponds to the electronic attack.14. The system of claim 10, wherein the processor executes thecomputer-executable instructions to: trigger an alarm, in response todetecting the interaction with the honey entity; analyze the interactionto determine if an interaction threshold is satisfied by theinteraction; and in response to determining that the interactionthreshold is satisfied, determine that the interaction corresponds tothe attack, blocking the attack, and propagating information relating tothe attack to a further entity within the private network.
 15. Thesystem of claim 14, wherein the processor executes thecomputer-executable instructions to: trigger an alarm, in response todetecting the interaction with the honey entity; analyze the interactionto determine if an interaction threshold is satisfied by theinteraction; determine that that the threshold is to be adjusted based,at least partially, upon determining that the threshold is satisfied anddetermining that the interaction does not correspond to the attack; andadjust the threshold.
 16. The system of claim 10, wherein the processorexecutes the computer-executable instructions to upload the honeyprofile to a social networking server accessible via the public network,the social networking server stores social networking data comprising aprofile associated with the real user.
 17. A computer storage mediumhaving computer-executable instructions stored thereon that, whenexecuted by a processor, cause the processor to perform operationscomprising: determining that a real user of a private network is atarget of an attacker; generating a honey user and a honey profile forthe honey user, the honey profile comprising a first version of contactinformation that differs from a second version of contact informationassociated with a real profile of the real user; exposing the honeyprofile outside of a private network associated with the real user;hosting honey entities at the private network; generating an instance ofhoney activity between a computer operating on the private network andthe honey entities; detecting an interaction with one honey entity ofthe honey entities; and determining, based upon detecting theinteraction with the honey entities, if the interaction corresponds toan attack by the attacker.
 18. The computer storage medium of claim 17,wherein the honey profile is exposed by uploading the honey profile to asocial networking server accessible via the public network, the socialnetworking server stores social networking data comprising the realprofile.
 19. The computer storage medium of claim 17, further comprisingcomputer-executable instructions that, when executed by the processor,cause the processor to perform operations further comprising: instruct amail server operating in communication with the private network to routea message intended for an email address associated with the honeyprofile to a honey computer; detect routing of the message to the honeycomputer; analyze the message to determine if the message comprises theattack; and trigger an alarm, in response to determining that themessage comprises the attack.
 20. The computer storage medium of claim19, further comprising computer-executable instructions that, whenexecuted by the processor, cause the processor to perform operationsfurther comprising: block the attack; and propagate informationassociated with the attack to other entities associated with the privatenetwork.